Search for: All records

Abstract To save saltmarshes and their valuable ecosystem services from sea level rise, it is crucial to understand their natural ability to gain elevation by sediment accretion. In that context, a widely accepted paradigm is that dense vegetation favors sediment accretion and hence saltmarsh resilience to sea level rise. Here, however, we reveal how dense vegetation can inhibit sediment accretion on saltmarsh platforms. Using a process‐based modeling approach to simulate biogeomorphic development of typical saltmarsh landscapes, we identify two key mechanisms by which vegetation hinders sediment transport from tidal channels toward saltmarsh interiors. First, vegetation concentrates tidal flow and sediment transport inside channels, reducing sediment supply to platforms. Second, vegetation enhances sediment deposition near channels, limiting sediment availability for platform interiors. Our findings suggest that the resilience of saltmarshes to sea level rise may be more limited than previously thought. 

The ocean plays a major role in controlling atmospheric carbon at decadal to millennial timescales, with benthic carbon representing the only geologic‐scale storage of oceanic carbon. Despite its importance, detailed benthic ocean observations are limited and representation of the benthic carbon cycle in ocean and Earth system models (ESMs) is mostly empirical with little prognostic capacity, which hinders our ability to properly understand the long‐term evolution of the carbon cycle and climate change‐related feedbacks. The Benthic Ecosystem and Carbon Synthesis (BECS) working group, with the support of the US Ocean Carbon & Biogeochemistry Program (OCB), identified key challenges limiting our understanding of benthic systems, opportunities to act on these challenges, and pathways to increase the representation of these systems in global modeling and observational efforts. We propose a set of priorities to advance mechanistic understanding and better quantify the importance of the benthos: (a) implementing a model intercomparison exercise with existing benthic models to support future model development, (b) data synthesis to inform both model parameterizations and future observations, (c) increased deployment of platforms and technologies in support of in situ benthic monitoring (e.g., from benchtop to field mesocosm), and (d) global coordination of a benthic observing program (“GEOSed”) to fill large regional data gaps and evaluate the mechanistic understanding of benthic processes acquired throughout the previous steps. Addressing these priorities will help inform solutions to both global and regional resource management and climate adaptation strategies. 

Abstract Developing sustainable software for the scientific community requires expertise in software engineering and domain science. This can be challenging due to the unique needs of scientific software, the insufficient resources for software engineering practices in the scientific community, and the complexity of developing for evolving scientific contexts. While open‐source software can partially address these concerns, it can introduce complicating dependencies and delay development. These issues can be reduced if scientists and software developers collaborate. We present a case study wherein scientists from the SuperNova Early Warning System collaborated with software developers from the Scalable Cyberinfrastructure for Multi‐Messenger Astrophysics project. The collaboration addressed the difficulties of open‐source software development, but presented additional risks to each team. For the scientists, there was a concern of relying on external systems and lacking control in the development process. For the developers, there was a risk in supporting a user‐group while maintaining core development. These issues were mitigated by creating a second Agile Scrum framework in parallel with the developers' ongoing Agile Scrum process. This Agile collaboration promoted communication, ensured that the scientists had an active role in development, and allowed the developers to evaluate and implement the scientists' software requirements. The collaboration provided benefits for each group: the scientists actuated their development by using an existing platform, and the developers utilized the scientists' use‐case to improve their systems. This case study suggests that scientists and software developers can avoid scientific computing issues by collaborating and that Agile Scrum methods can address emergent concerns.